IRIX Base Documentation 1998 November/IRIX 6.5.2 Base Documentation November 1998.img/usr/share/catman/u_man/cat1/cvpav.z/cvpav

Text File | 1998-10-30 | 30KB | 528 lines

CCCCVVVVPPPPAAAAVVVV((((1111))))                                                              CCCCVVVVPPPPAAAAVVVV((((1111))))



NNNNAAAAMMMMEEEE
     cvpav - present the information about an MP Fortran program from its
     MIPSpro 7.2 or higher analysis files

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     ccccvvvvppppaaaavvvv [[[[----eeee _e_x_e_c_u_t_a_b_l_e]]]] [[[[----ffff _f_i_l_e._f [[[[----aaaannnnllll _a_n_a_l_y_s_i_s]]]]]]]] [[[[----FFFF _f_i_l_e_s_e_t]]]] [[[[----rrrroooo
     {{{{_T_r_u_e|_F_a_l_s_e}}}}]]]] [[[[----sssscccchhhheeeemmmmeeee _s_c_h_e_m_e_N_a_m_e]]]]

DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
     _c_v_p_a_v reads the analysis file(s) generated by MIPSpro 7.2 or higher, for
     the files in a fileset, and displays information about the loops in the
     files in a window.  It allows the user to select any loop, request
     changes governing that loop, and then install those changes in the
     source.

     The analysis file is generated by MIPSpro 7.2 or higher, which is a
     prerequisite for WorkShop Pro MPF.  The analysis file contains the
     information currently shown on MIPSpro 7.2 or higher, listing file (*.l),
     and some additional information.  _c_v_p_a_v takes that information, and
     applies some heuristics to present it in a more comprehensible form with
     a graphical user interface.

     MIPSpro 7.2 or higher, may be invoked with the -_p_f_a _k_e_e_p flag on the _f_7_7
     command; the _k_e_e_p flag should always be used; otherwise the analysis file
     is not written, and _c_v_p_a_v can not be used.

CCCCOOOOMMMMMMMMAAAANNNNDDDD----LLLLIIIINNNNEEEE OOOOPPPPTTTTIIIIOOOONNNNSSSS
     _c_v_p_a_v accepts the following command-line options:

     ----eeee _e_x_e_c_u_t_a_b_l_e
          specifies a single executable file name as input; the fileset will
          consist of all the Fortran source files that went into building it.
          _c_v_p_a_v must always be invoked with the -_e flag if it is to be used
          with the WorkShop Performance Analyzer, to examine performance data
          recorded for the executable.

     ----ffff _f_i_l_e_n_a_m_e._f
          specifies a single Fortran source file name.

     ----aaaannnnllll _a_n_a_l_y_s_i_s
          specifies the analysis file, if not the default, corresponding to
          the Fortran file given by the ----ffff _f_i_l_e_n_a_m_e._f argument.  This argument
          is not normally needed.

     ----FFFF _f_i_l_e_s_e_t
          specifies a single text file name as input; the fileset will consist
          of the Fortran files whose names appear in the input file.  Each
          file name should be on a single line.

     ----rrrroooo {_T_r_u_e|_F_a_l_s_e}
          specifies whether _c_v_p_a_v will be able to modify the source files in
          the fileset (----rrrroooo FFFFaaaallllsssseeee) or not (----rrrroooo TTTTrrrruuuueeee)



                                                                        PPPPaaaaggggeeee 1111






CCCCVVVVPPPPAAAAVVVV((((1111))))                                                              CCCCVVVVPPPPAAAAVVVV((((1111))))



     ----sssscccchhhheeeemmmmeeee _s_c_h_e_m_e_N_a_m_e
          specifies which color scheme should be used for _c_v_p_a_v.

XXXX RRRREEEESSSSOOOOUUUURRRRCCCCEEEESSSS
     _c_v_p_a_v uses many resources to control its user interface, most of which
     should not be changed by the user.  Those that a user might want to
     change are:

     ccccvvvvppppaaaavvvv****rrrreeeeaaaaddddOOOOnnnnllllyyyy
          is a Boolean used to determine whether (False) or not (True) _c_v_p_a_v
          will allow the user to modify the files in its fileset.  It defaults
          to False.

     ccccvvvvppppaaaavvvv****ggggDDDDiiiiffffffff
          is a Boolean used to determine whether (True) or not (False) _c_v_p_a_v
          will automatically run _g_d_i_f_f to show changes in a source file when
          it is modified.  It defaults to False, so that no _g_d_i_f_f appears.

     ccccvvvvppppaaaavvvv****rrrruuuunnnnUUUUsssseeeerrrrEEEEddddiiiitttt
          is a Boolean used to determine whether (True) or not (False) _c_v_p_a_v
          will run the _u_s_e_r_E_d_i_t editor command after running the _s_e_d script.
          It defaults to False, so that no editor will be run; rather the new
          file will be built immediately.

     ccccvvvvppppaaaavvvv****eeeeddddiiiittttoooorrrrCCCCoooommmmmmmmaaaannnndddd
          is a string used as a command for a user to edit the file after _s_e_d
          and _g_d_i_f_f have been run on it.  It defaults to the following:
                    cvpav*editorCommand:   xwsh -e vi %d
          _Y_o_u _m_a_y _p_u_t _a_n _a_l_t_e_r_n_a_t_i_v_e _c_o_m_m_a_n_d _i_n _y_o_u_r ._X_d_e_f_a_u_l_t_s _f_i_l_e.  _T_h_e
          _c_o_m_m_a_n_d _s_t_r_i_n_g _s_h_o_u_l_d _i_n_v_o_k_e _a _w_i_n_d_o_w _s_h_e_l_l.  _I_f _i_t _c_o_n_t_a_i_n_s _a
          ``%_s'', _t_h_e _f_i_l_e_n_a_m_e _w_i_l_l _r_e_p_l_a_c_e _t_h_e ``%_s''; _i_f _n_o_t, _t_h_e _f_i_l_e_n_a_m_e
          _w_i_l_l _b_e _a_p_p_e_n_d_e_d.  _T_h_e _c_o_m_m_a_n_d _m_a_y _a_l_s_o _c_o_n_t_a_i_n _a ``%_d'' _w_h_i_c_h _w_i_l_l
          _b_e _r_e_p_l_a_c_e_d _b_y _a _1, _t_o _p_o_s_i_t_i_o_n _t_h_e _f_i_l_e _a_t _t_h_e _t_o_p _l_i_n_e.

     ccccvvvvppppaaaavvvv****sssscccchhhheeeemmmmeeee
          specifies the color and font scheme to be used for _c_v_p_a_v.

     ccccvvvvppppaaaavvvv****uuuusssseeeeSSSSmmmmaaaallllllllFFFFoooonnnnttttssss
          specifies that small fonts are to be used for _c_v_p_a_v in order to
          better use screen real-estate.  It defaults to False.

     ccccvvvvppppaaaavvvv****aaaannnnllllFFFFiiiilllleeeeSSSSuuuuffffffffiiiixxxx
          specifies the suffix used to construct an analysis file name from
          the corresponding source file.  It defaults to ._a_n_l corresponding to
          MIPSpro 7.2  or higher, normal output.

     ccccvvvvppppaaaavvvv****ttttrrrrssssrrrrccccFFFFiiiilllleeeeSSSSuuuuffffffffiiiixxxx
          specifies the suffix used to construct the name of the transformed
          source from the corresponding source file.  It defaults to ._m
          corresponding to MIPSpro 7.2  or higher, normal output.





                                                                        PPPPaaaaggggeeee 2222






CCCCVVVVPPPPAAAAVVVV((((1111))))                                                              CCCCVVVVPPPPAAAAVVVV((((1111))))



UUUUSSSSEEEERRRR IIIINNNNTTTTEEEERRRRFFFFAAAACCCCEEEE
     _c_v_p_a_v initially comes up with a menu bar, a status area, a list pane, a
     control region, and a Loop Information Pane.

   MMMMEEEENNNNUUUU BBBBAAAARRRR
     The ``Admin'' menu has entries to save the current data as a text file,
     to Generate a trap file for use by the WorkShop Performance Analyzer, to
     iconify or raise the windows of the Parallel Analyzer View, or to exit
     the tool, or to bring up the Icon Legend.  It also has a ``Launch Tool''
     submenu that will launch the other WorkShop tools, and a ``Project'' menu
     that will raise or iconify all windows in all tools within the project,
     remap paths to find source and analysis files, or exit all tools in the
     project.

     The ``Views'' menu allows the user to bring up the auxiliary Views. These
     are the Transformed Loops View, the Subroutine and File View, and the
     MIPSpro 7.2  or higher, Analysis Parameters View.

     The ``Fileset'' menu allows the user to add files to or delete files from
     the fileset.  It also contains an entry to rescan all the files.

     The ``Operations'' menu is used to undo changes to a single loop, or to
     undo all changes, and to insert new assertions or directives.

     The ``Configuration'' menu is used to give the user a choice between
     using OpenMP constructs and directives or old PCF style of constructs and
     directives.

     The ``Update'' menu is used to take any changes the user has requested,
     generate a _s_e_d script for them, and run that script on a single file, or
     on all files in the fileset.  It also has two toggles that can be used to
     control whether or not a _g_d_i_f_f is run to show the changes as made, and
     whether or not a user editor is invoked after the changes are made, but
     before the rebuild is started.  The default settings for the toggles are
     taken from the corresponding resources.

     The ``Help'' menu is used to access on-line help for _c_v_p_a_v.

   TTTTHHHHEEEE SSSSTTTTAAAATTTTUUUUSSSS AAAARRRREEEEAAAA
     The status area is used to inform the user of the current status of the
     program, as well as to describe any performance experiment that is in the
     current project.

   TTTTHHHHEEEE LLLLOOOOOOOOPPPP LLLLIIIISSSSTTTT
     The upper subpane in the main window is the Loop List.  It contains a
     scrolled list of all the loops in the files belonging to the fileset,
     with information about the nesting level, and description of each loop.
     Each loop has an icon next to it which indicates whether the loop is
     parallel, serial, serial within a parallel loop, optimized away, fused
     with another loop, or unparallelizable.  In addition, a check mark
     appears next to any loop that has been displayed in the Loop Information
     Pane (see below), and a plus sign next to the check mark if the user has



                                                                        PPPPaaaaggggeeee 3333






CCCCVVVVPPPPAAAAVVVV((((1111))))                                                              CCCCVVVVPPPPAAAAVVVV((((1111))))



     requested any changes to that loop.  The icons are colored differently to
     show parallel loops, unparallelizable loops, and the various kinds of
     serial loops.  The colors used will match the loop annotation brackets
     that appear on the two SourceViews that may be brought up.

     A loop may be selected by double-clicking on the line in the Loop List
     showing that loop.  The ``Next'' and ``Previous'' buttons may be used to
     step forwards and backwards through the list.  If no loop is selected,
     the ``Next'' and ``Previous'' buttons will select the first loop on the
     list.  A loop may also be selected by clicking in the loop annotation
     canvas in either SourceView.

   TTTTHHHHEEEE CCCCOOOONNNNTTTTRRRROOOOLLLL AAAARRRREEEEAAAA
     The control area contains a search field to find a loop based on any
     string appearing in its line, sorting and filtering controls, and a row
     of buttons.  The search field is in the upper left of the control area.

     The sort menu is in the middle left of the control area.  It allows
     sorting in the order the loops appear in the source, or if a Performance
     Analyzer is part of the current session, in order of performance cost.
     If the Performance Analyzer is not part of the session, the menu entry
     for sorting by performance cost will be disabled.

     Two filtering controls can be used to prune the list.  One filters the
     list according to the type (parallelized, unparallelizable, serial,
     OpenMP constructs, or modified) of the loops, and the other filters on
     the basis of either the function (subroutine) or file from which the loop
     comes.  A text area for entering the name of a function or file will
     appear above the menu when one of the filtering menu entries is selected.
     Double clicking on a function or file line in the Subroutines and Files
     View (see below) will select that function or file, and, if the filtering
     is enabled, will reload the list.  Both types of filters may be used
     simultaneously.  If a previously selected loop is in the list after
     changing the filtering, it will remain selected; if not, no loop will be
     selected.

     At the bottom of the control area are buttons to bring up the source for
     the loop, to bring up the transformed source for the loops derived from
     that loop, and to step to the next or previous loop.

   TTTTHHHHEEEE LLLLOOOOOOOOPPPP IIIINNNNFFFFOOOORRRRMMMMAAAATTTTIIIIOOOONNNN PPPPAAAANNNNEEEE
     The lower subpane of the main window is the Loop Information Pane.  It
     shows detailed information for whatever loop is currently selected from
     the Loop List; if no loop is selected, it contains a single line to that
     effect.

     The Loop Information Pane shows the loop identification information, and
     the parallelization status for the loop, with a menu that allows the user
     to insert directives controlling the parallelization of the loop.
     Similarly there is a menu for controlling the MP-scheduling of a parallel
     loop, and a filed for the chunk size to be used; these controls are not
     meaningful for a non-parallel loop.  The pane also shows any assertions



                                                                        PPPPaaaaggggeeee 4444






CCCCVVVVPPPPAAAAVVVV((((1111))))                                                              CCCCVVVVPPPPAAAAVVVV((((1111))))



     or directives controlling the selected loop, and, where applicable, a
     menu allowing the user to keep or delete them.  (Those assertions and
     directives that control parallelization of the loop do not have menus, as
     they are handled by the parallelization status menu; For loops that can
     not be parallelized, it shows the reasons MIPSpro 7.2  or higher, can not
     parallelize it.  The changes will not actually be installed in the source
     until the update of the file containing that loop is requested using the
     ``Update'' menu.

     Some of the lines appearing in the Loop Information Pane have small
     buttons containing a light-bulb icon next to them.  A left mouse click on
     any of those buttons will bring up and highlight the source for that
     loop, marking the line(s) or names that apply to the particular line of
     information selected.  For names of variables or functions, the
     highlighting is applied only within the loop that has been selected,
     rather than within the entire file.

     Highlighting variable or function names is done as a token highlight; it
     will attempt to use FORTRAN rules to determine whether an instance of the
     named variable is really a reference to the variable or if it is a string
     that coincidentally matches.  It will miss some matches, where, for
     example, the user has inserted spaces in the middle of the name, or uses
     a letter in column 6 to indicate a continuation line and no space between
     it and the variable reference.  The WorkShop 2.0/Static Analyzer can be
     used for a semantically correct search and highlight, since it is based
     on information output by the FORTRAN compiler.

     Once all changes for a particular file have been made, the ``Update''
     menu can be used to install those changes in the source.  When invoked,
     the file will be moved to a backup file, and a _s_e_d script will be written
     and run to install the changes.  If requested, _g_d_i_f_f will be run to show
     the changes and/or an editor will be invoked to allow additional user
     changes.  After the exit from _g_d_i_f_f and/or the editor, the WorkShop Build
     Analyzer will be invoked to start a rebuild from the modified sources.
     It depends on the existence of a Makefile for that purpose.  If one
     exists, and is properly set up, hit the ``Build'' button on the Build
     Analyzer, and the rebuild will be started.  When it completes, it will
     tell _c_v_p_a_v, which will automatically rescan the file.  If no Makefile
     exists, the Build Analyzer will report the error, and _c_v_p_a_v will post an
     error asking that _c_v_M_I_P_S_p_r_o _7._2 _o_r _h_i_g_h_e_r, be run by hand, and that the
     user then invoke ``Rescan All Files'' from the ``Fileset'' menu.

     If _c_v_p_a_v is brought up on a program whose analysis file was written by an
     earlier version of MIPSpro 7.2 or higher, it will post a warning saying
     the version string was from an older version.  Although it will still
     work, you should rebuild the analysis file with the latest version.

   TTTTHHHHEEEE PPPPAAAARRRRAAAALLLLLLLLEEEELLLLIIIIZZZZAAAATTTTIIIIOOOONNNN IIIICCCCOOOONNNN LLLLEEEEGGGGEEEENNNNDDDD
     The Icon Legend is brought up from the ``Admin'' menu.  It shows each of
     the icons that are used to describe the parallelization state of any loop
     in the Loop List, the Loop Information Pane, and the Transformed Loops
     View, and gives their meaning.  It also shows the icons used to describe



                                                                        PPPPaaaaggggeeee 5555






CCCCVVVVPPPPAAAAVVVV((((1111))))                                                              CCCCVVVVPPPPAAAAVVVV((((1111))))



     the read/write status of each of the variables in the loop shown in the
     Custom DOACROSS Dialog, along with their meanings.  Finally, it also
     shows the icons used in the Subroutines and Files view.

   TTTTHHHHEEEE OOOORRRRIIIIGGGGIIIINNNNAAAALLLL AAAANNNNDDDD TTTTRRRRAAAANNNNSSSSFFFFOOOORRRRMMMMEEEEDDDD SSSSOOOOUUUURRRRCCCCEEEEVVVVIIIIEEEEWWWWSSSS
     There are two SourceViews that may be brought up on a loop, one to show
     the original source, and one to show the source as transformed by MIPSpro
     7.2  or higher.  They are brought up with buttons at the bottom of the
     control panel of the main window.  When either SourceView is brought up,
     it will be annotated with loop information, appearing as brackets
     indicating the range of a loop.  The brackets are coded to match the
     colors of the icons describing the parallelization state of the loop.
     Clicking the mouse on a bracket will select that loop, either original or
     transformed, and cause all the other windows to update to reflect the
     selection.  Clicking outside the outer bracket will select the outermost
     loop; clicking inside the inner bracket will select the innermost loop.
     Clicking on a line that is not within any loop will be ignored.

     The Transformed SourceView also will have a vertical bar in the same
     color as the highlighting of an original loop in the Original SourceView
     next to each loop in the transformed source that is derived from the
     selected original loop.

     If the project also includes a Performance Tool, the SourceViews will
     additionally be annotated with line-level performance information.  For
     any particular file, only one of the two SourceViews will get performance
     annotations (the SourceView corresponding to the file that has its line
     number information in the symbol table).

   TTTTHHHHEEEE TTTTRRRRAAAANNNNSSSSFFFFOOOORRRRMMMMEEEEDDDD LLLLOOOOOOOOPPPPSSSS VVVVIIIIEEEEWWWW
     The Transformed Loops View is brought up from the ``Views'' menu.  It
     lists all the loops into which the selected original source loop was
     transformed.  The first line of description of each loop gives that
     loop's transformed-ID (an integer).  It also has a highlight button which
     is sensitive to a left-mouse click, and which will show the original
     source of the program, highlighting those lines that went into the
     transformed loop.  Other lines show messages associated with the
     transformed loop.  Those lines that have highlight buttons are sensitive
     to left-mouse clicks; clicking on them will mark the relevant source
     lines.  When writing the transformed source, MIPSpro 7.2 or higher, will
     insert lines bracketing each transformed loop; these lines are of the
     form:
                         CSGI$ start _n_n_n
                         CSGI$ end _n_n_n
     _w_h_e_r_e _n_n_n _i_s _t_h_e _t_r_a_n_s_f_o_r_m_e_d-_I_D _o_f _t_h_e _l_o_o_p.  _I_f _t_h_e _t_r_a_n_s_f_o_r_m_e_d _s_o_u_r_c_e
     _i_s _b_e_i_n_g _s_h_o_w_n, _w_h_e_n _a_n_y _o_f _t_h_e _l_i_n_e_s _l_i_s_t_i_n_g _a _t_r_a_n_s_f_o_r_m_e_d _l_o_o_p _i_n _t_h_i_s
     _w_i_n_d_o_w _i_s _c_l_i_c_k_e_d, _i_t_s _s_o_u_r_c_e _v_i_e_w _w_i_l_l _h_i_g_h_l_i_g_h_t _a_l_l _t_h_e _l_i_n_e_s _b_e_t_w_e_e_n
     _t_h_e _s_t_a_r_t _a_n_d _e_n_d _l_i_n_e_s _f_o_r _t_h_a_t _l_o_o_p, _m_a_r_k _t_h_e_i_r _p_o_s_i_t_i_o_n _i_n _t_h_e
     _s_c_r_o_l_l_b_a_r, _a_n_d _s_c_r_o_l_l _t_o _t_h_e _s_t_a_r_t _l_i_n_e.  _I_t _w_i_l_l _a_l_s_o _h_i_g_h_l_i_g_h_t _a_l_l
     _l_i_n_e_s _i_n _t_h_e _o_r_i_g_i_n_a_l _S_o_u_r_c_e_V_i_e_w _t_h_a_t _w_e_n_t _i_n_t_o _t_h_e _s_e_l_e_c_t_e_d _T_r_a_n_s_f_o_r_m_e_d
     _L_o_o_p.



                                                                        PPPPaaaaggggeeee 6666






CCCCVVVVPPPPAAAAVVVV((((1111))))                                                              CCCCVVVVPPPPAAAAVVVV((((1111))))



   TTTTHHHHEEEE SSSSUUUUBBBBRRRROOOOUUUUTTTTIIIINNNNEEEESSSS AAAANNNNDDDD FFFFIIIILLLLEEEESSSS VVVVIIIIEEEEWWWW
     The Subroutines and Files View is brought up from the ``Views'' menu.  It
     consists of a scrolled list of all the files in the fileset, and the
     functions contained in each.

     For a file, the view lists the status of that file, and the date at which
     the source was last modified.  Files that were not scanned will get an
     icon with an international ``not'' sign; those which were scanned with no
     errors will get a check mark.  If the user has requested changes in any
     of the loops within the file, a plus sign appears next to the check for
     the file.

     For a subroutine, the view shows if there were any syntax errors in it,
     and it shows the source lines for the function.  Functions with syntax
     errors will get an icon with an international ``not'' sign; those with no
     errors will get a check mark.

     Double clicking on a line in this view will select the file or subroutine
     which it describes, and, if file or subroutine filtering is enabled, will
     reload the list of loops.

   TTTTHHHHEEEE CCCCUUUUSSSSTTTTOOOOMMMM DDDDOOOOAAAACCCCRRRROOOOSSSSSSSS DDDDIIIIAAAALLLLOOOOGGGG
     The Custom ``DOACROSS''/``OMP PARALLEL DO'' Dialog is brought up by
     selecting ``DOACROSS...''  from the loop status menu in the Loop
     Information Pane.  It shows all variables within the loop, with a menu
     used to select whether they should be treated as local, shared, last-
     local, or as a reduction variable.  Each variable has a highlight button
     next to it, which can be used to highlight uses of the variable within
     the loop.  Each also has an icon next to it indicating whether the
     variable is read, written, or both.

     The DOACROSS Dialog also has a menu for setting the MP scheduling and a
     text field for entering a chunk size.  It also has text fields for
     affinity, onto, and nest; these are new directives that are supported by
     MIPSpro 7.2 or higher.  It also has a text-entry field to optionally
     enter an expression that will determine at run-time whether the loop
     should be run in serial or parallel.

     When the user is finished composing the custom DOACROSS for a loop, he or
     she must hit either ``Apply'' to make the changes take, or ``Cancel'' to
     undo them.  The changes will not actually be installed in the source
     until the update of the file containing that loop is requested using the
     ``Update'' menu.  If the user attempts to switch to a different loop (or
     perform any manipulation of the fileset or filtering or attempt to exit)
     with the Custom DOACROSS Dialog up, the program will post a warning
     asking the user to hit either Apply or Cancel first.

   TTTTHHHHEEEE CCCCUUUUSSSSTTTTOOOOMMMM OOOOMMMMPPPP PPPPAAAARRRRAAAALLLLLLLLEEEELLLL DDDDOOOO DDDDIIIIAAAALLLLOOOOGGGG
     The Custom OMP PARALLEL DO Dialog is brought up by selecting ``OMP
     PARALLEL DO..''  from the loop status menu in the Loop Information Pane.
     It shows all variables within the loop, with a menu used to select
     whether they should be treated as local, shared, last-local, or as a



                                                                        PPPPaaaaggggeeee 7777






CCCCVVVVPPPPAAAAVVVV((((1111))))                                                              CCCCVVVVPPPPAAAAVVVV((((1111))))



     reduction variable.  Each variable has a highlight button next to it,
     which can be used to highlight uses of the variable within the loop.
     Each also has an icon next to it indicating whether the variable is read,
     written, or both.

     The OMP PARALLEL DO Dialog also has a menu for setting the MP scheduling
     and a text field for entering a chunk size.  It also has text fields for
     local, shared, default, firstlocal, lastlocal, copyin, reduction,
     affinity, onto, and nest; these are new directives that are supported by
     MIPSpro 7.2.1.  It also has a text-entry field to optionally enter an
     expression that will determine at run-time whether the loop should be run
     in serial or parallel.

     When the user is finished composing the custom OMP PARALLEL DO for a
     loop, he or she must hit either ``Apply'' to make the changes take, or
     ``Cancel'' to undo them.  The changes will not actually be installed in
     the source until the update of the file containing that loop is requested
     using the ``Update'' menu.  If the user attempts to switch to a different
     loop (or perform any manipulation of the fileset or filtering or attempt
     to exit) with the Custom OMP PARALLEL DO dialog up, the program will post
     a warning asking the user to hit either Apply or Cancel first.

     If the source file can not be written, or if the read-only flag is
     supplied as True on the command line or as an X resource, none of the
     control menus will be operative.  Also, if a particular loop comes from
     an included source file, rather than a file explicitly named in the
     fileset, it will be treated as read-only, as the program can not tell
     what effects changing one instance of an included file might have on
     other instances of it.

EEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnntttt VVVVaaaarrrriiiiaaaabbbblllleeeessss
     You can turn off Software Pipelining messages by setting MPF_TESTING
     environment variable

     sssseeeetttteeeennnnvvvv MMMMPPPPFFFF____TTTTEEEESSSSTTTTIIIINNNNGGGG


SSSSEEEEEEEE AAAALLLLSSSSOOOO
     cvd(1), cvperf(1), cvbuild(1),  gdiff(1), sed(1)

BBBBUUUUGGGGSSSS
     The detailed list of known problems is given in the release notes chapter
     3; please examine it there.












                                                                        PPPPaaaaggggeeee 8888